[Fix] Link up notifications LINK_UP_TIMER
#114
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #101
Fixes #100
Fixes #103 (it's using
notified_up_at
metadata though)LINK_UP_TIMER
has passedlink_status_hook_link_up_timer
to updatestatus
accordingly.notified_up_at
internal reserved metadataNow it's correctly respecting
LINK_UP_TIMER
, the following cases were explored locally (I've also left some requests to pathfinder in the background running for additional testing):1 - Both interface go up and created in a short period:
Notice that
mef_eline
is notified in 10 secs more of less[2022-11-18 14:43:30,776 - INFO [kytos.napps.kytos/mef_eline] [main.py:630:on_link_up]
once handshake and port description were received:2 - Set interface down and up shortly after:
3 - Make sure it's working well with liveness since it's relying on
status
:Notice that it notified link up only once, even if liveness detects it faster, but since it's now integrated with
stauts
and status_funcs then it respects accordingly: